-
Notifications
You must be signed in to change notification settings - Fork 78
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Enhance Audit Log Data Beyond Privacy Requests #3331
Conversation
Passing run #2215 ↗︎
Details:
This comment has been generated by cypress-bot as a result of this project's GitHub integration settings. |
@seanpreston I think this is the same implementation that is used elsewhere but doesn't seem to yield the same result. I have thrown breakpoints on it and watched it through a few different ways. One caveat is to see it working elsewhere, you also need to create a different user and sign in as that user.
…8-audit-log-resource
Codecov ReportPatch coverage:
Additional details and impacted files@@ Coverage Diff @@
## main #3331 +/- ##
==========================================
- Coverage 87.24% 87.12% -0.12%
==========================================
Files 311 312 +1
Lines 18587 18659 +72
Branches 2368 2377 +9
==========================================
+ Hits 16216 16257 +41
- Misses 1955 1981 +26
- Partials 416 421 +5
☔ View full report in Codecov by Sentry. |
@seanpreston still adding some more tests but wanted to at least get this back on the radar so it can go with the release - thanks again for the help!! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
overall i think this looks like a really solid first iteration @SteveDMurphy. the code is pretty easy to follow, i like how you've organized things and you've set up a great foundation! gating this behind a config var (that defaults to false) i think is a great and necessary choice to get this out in the wild while mitigating any risk.
i've got some minor cleanup comments, some of which would be nice to address before merging, i think. beyond that, there are a couple of more "meaty" questions about how we can ensure this all runs properly in the background and stays decoupled from actual API/application tasks - as i note in the comments, i don't think these need to block this initial iteration, but i believe they should be seriously considered before we're ready to deploy this in a production (or any client) environment.
let me know what you think and if you'd like to link up at all to discuss!
Co-authored-by: Adam Sachs <[email protected]>
Co-authored-by: Adam Sachs <[email protected]>
merging in |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks great as a first iteration, follow ups have been noted and issues will be created 👍
Co-authored-by: Adam Sachs <[email protected]>
Closes fde#8
Code Changes
GET
data to the servermiddleware.py
to house functionalitySteps to Confirm
FIDES__SECURITY__ENABLE_AUDIT_LOG_RESOURCE_MIDDLEWARE: "True"
to the compose file then runningnox -s dev
POST
orPUT
select * from public.audit_log_resource;
)Pre-Merge Checklist
CHANGELOG.md
Description Of Changes
This PR will address the who and when with a high-level what more than the what (detail) has changed. A design doc will follow as part of this issue closure.
Interestingly, the new middleware severely impacted pytest (i.e. it didn't run). Adding the config variable to disallow it was an option I was already interested in but became a necessity for that reason.